Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a076c1d0fa6fcbb10d5572ed76ddb57b7bc57203957137d8081e9545d0fc90aa

Tx prefix hash: d2c95551760bf5a2b4ec3ecdf2887db2da1aa58b69182cfa6fd3fe8b1f999991
Tx public key: 02d113fc8f3bb598660dc9c406d518aab84e64cc76f95f929e8f8f1bcefd5b05
Timestamp: 1750924121 Timestamp [UCT]: 2025-06-26 07:48:41 Age [y:d:h:m:s]: 00:147:20:13:26
Block: 1313043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103647 RingCT/type: yes/0
Extra: 0102d113fc8f3bb598660dc9c406d518aab84e64cc76f95f929e8f8f1bcefd5b05021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b644dab808684aec3a3fd5005198e41c773ed83a61f49d77d6c12fe54d029b7 0.600000000000 1800680 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": 1313053, "vin": [ { "gen": { "height": 1313043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b644dab808684aec3a3fd5005198e41c773ed83a61f49d77d6c12fe54d029b7" } } ], "extra": [ 1, 2, 209, 19, 252, 143, 59, 181, 152, 102, 13, 201, 196, 6, 213, 24, 170, 184, 78, 100, 204, 118, 249, 95, 146, 158, 143, 143, 27, 206, 253, 91, 5, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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