Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1ba71bc3d39275cc9521cca4a453bca93292a0e63e2762a8dac1c16a68a82dad

Tx prefix hash: a99a17859dd6de80ef5a1546887ce090ea99432a3d9f2868a18f1c100abfe551
Tx public key: 8a9760a837f0a3581a2ef660d48249ed1d19d5d3e7a75135a4efe4a212e179d2
Timestamp: 1723316030 Timestamp [UCT]: 2024-08-10 18:53:50 Age [y:d:h:m:s]: 00:158:03:38:55
Block: 1085045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113133 RingCT/type: yes/0
Extra: 018a9760a837f0a3581a2ef660d48249ed1d19d5d3e7a75135a4efe4a212e179d202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0661fb486a508a049e6a82bf899b1ef2a96acbc4cc7248a881f2a0ea2c3ef121 0.600000000000 1559534 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1085055, "vin": [ { "gen": { "height": 1085045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0661fb486a508a049e6a82bf899b1ef2a96acbc4cc7248a881f2a0ea2c3ef121" } } ], "extra": [ 1, 138, 151, 96, 168, 55, 240, 163, 88, 26, 46, 246, 96, 212, 130, 73, 237, 29, 25, 213, 211, 231, 167, 81, 53, 164, 239, 228, 162, 18, 225, 121, 210, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8