Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 308117ec9d68710aa22f43f69f97694f36fdaf50866a39e2a9f6c17cac90a743

Tx prefix hash: 51ce81caa9885f2f698e76dc792595c2b5a6119da2ace781d0f0de4ab74ea29f
Tx public key: 396a3ca5cfe6726fa2280cd221ac116f40bcbce0ae49dd6df8f602b08966d648
Timestamp: 1749830873 Timestamp [UCT]: 2025-06-13 16:07:53 Age [y:d:h:m:s]: 00:153:16:44:33
Block: 1304234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107606 RingCT/type: yes/0
Extra: 01396a3ca5cfe6726fa2280cd221ac116f40bcbce0ae49dd6df8f602b08966d6480211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1fb8ec749aaf0a39d198c43db4ab56032afca1d91e5320ff047d74fbbbe5b4b 0.600000000000 1791821 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": 1304244, "vin": [ { "gen": { "height": 1304234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1fb8ec749aaf0a39d198c43db4ab56032afca1d91e5320ff047d74fbbbe5b4b" } } ], "extra": [ 1, 57, 106, 60, 165, 207, 230, 114, 111, 162, 40, 12, 210, 33, 172, 17, 111, 64, 188, 188, 224, 174, 73, 221, 109, 248, 246, 2, 176, 137, 102, 214, 72, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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