Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cce5c1be9bc6e1c1a6ed6d9bd42678b538357295718825a7c858ed96a24a160

Tx prefix hash: 57a01cf11644ba73291f3f4d5967a653a6e5edfd0ea235b2448bf893ed35ea54
Tx public key: 143c5cc8e7f970ec36e0e311c0996aafe9915553ce511005d84f0c658d56a257
Timestamp: 1749633913 Timestamp [UCT]: 2025-06-11 09:25:13 Age [y:d:h:m:s]: 00:151:18:47:00
Block: 1302664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106170 RingCT/type: yes/0
Extra: 01143c5cc8e7f970ec36e0e311c0996aafe9915553ce511005d84f0c658d56a257021100000006e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6927b20eef69ebfb057d59336a6ab6e6f8aa9e3fa0c1303bb3219bc0bf4196f8 0.600000000000 1790237 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": 1302674, "vin": [ { "gen": { "height": 1302664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6927b20eef69ebfb057d59336a6ab6e6f8aa9e3fa0c1303bb3219bc0bf4196f8" } } ], "extra": [ 1, 20, 60, 92, 200, 231, 249, 112, 236, 54, 224, 227, 17, 192, 153, 106, 175, 233, 145, 85, 83, 206, 81, 16, 5, 216, 79, 12, 101, 141, 86, 162, 87, 2, 17, 0, 0, 0, 6, 228, 220, 144, 9, 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