Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241cbf4ca0300367eca1612e61a7487dc3b2d2c57d87d88faaf11630c1d325ff

Tx prefix hash: 298a2da040b28955415d38773be984027ff1153b6a6acac08411681aac893ebd
Tx public key: 6ce3f1bb6f0dfd8aa2e31698745fabd26a766c8aa1dd07efe0cc73500ce6712f
Timestamp: 1737138414 Timestamp [UCT]: 2025-01-17 18:26:54 Age [y:d:h:m:s]: 00:058:16:50:05
Block: 1199492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41746 RingCT/type: yes/0
Extra: 016ce3f1bb6f0dfd8aa2e31698745fabd26a766c8aa1dd07efe0cc73500ce6712f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b437a0c533d9ccbb604eaf085b50f9bcf6a42d176c7be8bf2da965d3ce6a7b5 0.600000000000 1686123 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": 1199502, "vin": [ { "gen": { "height": 1199492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b437a0c533d9ccbb604eaf085b50f9bcf6a42d176c7be8bf2da965d3ce6a7b5" } } ], "extra": [ 1, 108, 227, 241, 187, 111, 13, 253, 138, 162, 227, 22, 152, 116, 95, 171, 210, 106, 118, 108, 138, 161, 221, 7, 239, 224, 204, 115, 80, 12, 230, 113, 47, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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