Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1b5e702bcfd6e3713afb92aef59e46bad3d4942c3661bda4f6e0332cfdc6436

Tx prefix hash: b03809091f490de5732bc69e8cc314837b07faf6820e6cd4609e39755580e2d8
Tx public key: 2a1f1b76ad0ff8c0e8885e1a90466ebf68f666ace9f4f64d78f6e0f297168a28
Timestamp: 1649376740 Timestamp [UCT]: 2022-04-08 00:12:20 Age [y:d:h:m:s]: 02:214:22:25:53
Block: 475473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 673347 RingCT/type: yes/0
Extra: 012a1f1b76ad0ff8c0e8885e1a90466ebf68f666ace9f4f64d78f6e0f297168a2802110000000206faf294000000000000000000

1 output(s) for total of 16.314213382000 dcy

stealth address amount amount idx
00: a11d79edd702dadca617092438f5c919636536baec9cbb63d0eb1c65196d4ffd 16.314213382000 895724 of 0

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": 475483, "vin": [ { "gen": { "height": 475473 } } ], "vout": [ { "amount": 16314213382, "target": { "key": "a11d79edd702dadca617092438f5c919636536baec9cbb63d0eb1c65196d4ffd" } } ], "extra": [ 1, 42, 31, 27, 118, 173, 15, 248, 192, 232, 136, 94, 26, 144, 70, 110, 191, 104, 246, 102, 172, 233, 244, 246, 77, 120, 246, 224, 242, 151, 22, 138, 40, 2, 17, 0, 0, 0, 2, 6, 250, 242, 148, 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