Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d37eedd0357fdaeee0ef5a99e1f39e4baefda56a353c0fe93ccda00e68df456

Tx prefix hash: 033d271376f23332f17f189cfef1fe74a9ff6f85731b7560b2a2b8af67417e16
Tx public key: d02e49622af6fe3dcadaed01378a62b2ff4385849c48e6c0d0b8e720e02e8c90
Timestamp: 1726846243 Timestamp [UCT]: 2024-09-20 15:30:43 Age [y:d:h:m:s]: 00:235:17:55:05
Block: 1114311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168340 RingCT/type: yes/0
Extra: 01d02e49622af6fe3dcadaed01378a62b2ff4385849c48e6c0d0b8e720e02e8c90021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6553f24d776e6bde9bcfcad85b40d9ab9aebb9e0c6d8fad2df6c92f9c9ee2703 0.600000000000 1594110 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": 1114321, "vin": [ { "gen": { "height": 1114311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6553f24d776e6bde9bcfcad85b40d9ab9aebb9e0c6d8fad2df6c92f9c9ee2703" } } ], "extra": [ 1, 208, 46, 73, 98, 42, 246, 254, 61, 202, 218, 237, 1, 55, 138, 98, 178, 255, 67, 133, 132, 156, 72, 230, 192, 208, 184, 231, 32, 224, 46, 140, 144, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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