Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 417e5bffaf1fdfb35dc141f49865bed1c0962ba3e832d8feaa206fc0f76a2cdb

Tx prefix hash: f11d538dab102e68ef606825fc724c0a1db9a38bffeb943262fd7e957ec1137e
Tx public key: 27f034d71dabe8a1a0fcf90a237f1d67bfd208e7fe90056ccfc52e36dc432203
Timestamp: 1701450042 Timestamp [UCT]: 2023-12-01 17:00:42 Age [y:d:h:m:s]: 01:131:14:34:17
Block: 903761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355228 RingCT/type: yes/0
Extra: 0127f034d71dabe8a1a0fcf90a237f1d67bfd208e7fe90056ccfc52e36dc43220302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.621533606000 dcy

stealth address amount amount idx
00: da41231063a3ad11ff03ece5a81356df599f91116f4cab793000bb88f1db8aca 0.621533606000 1360452 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": 903771, "vin": [ { "gen": { "height": 903761 } } ], "vout": [ { "amount": 621533606, "target": { "key": "da41231063a3ad11ff03ece5a81356df599f91116f4cab793000bb88f1db8aca" } } ], "extra": [ 1, 39, 240, 52, 215, 29, 171, 232, 161, 160, 252, 249, 10, 35, 127, 29, 103, 191, 210, 8, 231, 254, 144, 5, 108, 207, 197, 46, 54, 220, 67, 34, 3, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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