Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09e21c4d360c680ad104d764ca5376bd37c1d69e4be2a658ed798712e6a8f7be

Tx prefix hash: 2c894d711d14c6862168fe844f4fd29e00d8218d871acb9d3d3bd42a361cdb51
Tx public key: cf0bd15d33b3d81df29b3ab243157a37f8d41494cc8bf04d92554d5899cd782a
Timestamp: 1728139757 Timestamp [UCT]: 2024-10-05 14:49:17 Age [y:d:h:m:s]: 01:035:19:14:20
Block: 1125038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283969 RingCT/type: yes/0
Extra: 01cf0bd15d33b3d81df29b3ab243157a37f8d41494cc8bf04d92554d5899cd782a021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5d772d7103148ab9589501e5a67e4ca45d3783ac2ac79a5fdcb64fd10091b93 0.600000000000 1607711 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": 1125048, "vin": [ { "gen": { "height": 1125038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5d772d7103148ab9589501e5a67e4ca45d3783ac2ac79a5fdcb64fd10091b93" } } ], "extra": [ 1, 207, 11, 209, 93, 51, 179, 216, 29, 242, 155, 58, 178, 67, 21, 122, 55, 248, 212, 20, 148, 204, 139, 240, 77, 146, 85, 77, 88, 153, 205, 120, 42, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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