Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3cbe91911686d3fd2236728017b9793a5a03e6c48f1b7168fb5e97cc604fa91

Tx prefix hash: 9bc51611c2b7d89211fade4510f64eed3fc9bbc7786c295aa229b9128c56b19b
Tx public key: ac8e8bcbb671e570b36b0044233ecbac0c925f70ad6d97b0bf589812ec0a2f17
Timestamp: 1751832459 Timestamp [UCT]: 2025-07-06 20:07:39 Age [y:d:h:m:s]: 00:137:18:57:04
Block: 1320147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96873 RingCT/type: yes/0
Extra: 01ac8e8bcbb671e570b36b0044233ecbac0c925f70ad6d97b0bf589812ec0a2f17021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec5bad8669a0d9edf30fba531c559d420ef49c53f98acaed75f492d971d05f2d 0.600000000000 1807842 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": 1320157, "vin": [ { "gen": { "height": 1320147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec5bad8669a0d9edf30fba531c559d420ef49c53f98acaed75f492d971d05f2d" } } ], "extra": [ 1, 172, 142, 139, 203, 182, 113, 229, 112, 179, 107, 0, 68, 35, 62, 203, 172, 12, 146, 95, 112, 173, 109, 151, 176, 191, 88, 152, 18, 236, 10, 47, 23, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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