Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a45d443f9b70e3abe18d2f32abb2345777509ca14d33f211502ab2c4f5c68e59

Tx prefix hash: 552447583ea62a6c8c10b77480f996a93ac40214b26110b04e116c4e06ac42a3
Tx public key: 0cccde3658428482b6b1bf0c8d8e6e4e4aead42260b9a127c9251583a59ff7a0
Timestamp: 1741265209 Timestamp [UCT]: 2025-03-06 12:46:49 Age [y:d:h:m:s]: 00:006:05:19:10
Block: 1233397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4459 RingCT/type: yes/0
Extra: 010cccde3658428482b6b1bf0c8d8e6e4e4aead42260b9a127c9251583a59ff7a0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01dd01e14d9282485e16b2a22be76e192df4475567dccd4efd469e1defde02f1 0.600000000000 1720318 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": 1233407, "vin": [ { "gen": { "height": 1233397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01dd01e14d9282485e16b2a22be76e192df4475567dccd4efd469e1defde02f1" } } ], "extra": [ 1, 12, 204, 222, 54, 88, 66, 132, 130, 182, 177, 191, 12, 141, 142, 110, 78, 74, 234, 212, 34, 96, 185, 161, 39, 201, 37, 21, 131, 165, 159, 247, 160, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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