Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1941e5eed5b919d9262ea2e2bb154cd694a8530fae7ad7fcbc28cf2c407fe5b

Tx prefix hash: 083c6a79d22155c39bb6897ee13b588b1daa2e04f41532abc83fe05c8c094c42
Tx public key: 3580dec74681a9f5e9a52dff8cda8d15eaa840e7264106643d9007043bcf1521
Timestamp: 1753276215 Timestamp [UCT]: 2025-07-23 13:10:15 Age [y:d:h:m:s]: 00:117:10:37:00
Block: 1331663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82765 RingCT/type: yes/0
Extra: 013580dec74681a9f5e9a52dff8cda8d15eaa840e7264106643d9007043bcf152102110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83abc3206683868c8cb22b718f27e3f61d170b9fa5ae20e862e905b22f5f150f 0.600000000000 1819460 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": 1331673, "vin": [ { "gen": { "height": 1331663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83abc3206683868c8cb22b718f27e3f61d170b9fa5ae20e862e905b22f5f150f" } } ], "extra": [ 1, 53, 128, 222, 199, 70, 129, 169, 245, 233, 165, 45, 255, 140, 218, 141, 21, 234, 168, 64, 231, 38, 65, 6, 100, 61, 144, 7, 4, 59, 207, 21, 33, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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