Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8ada6d69ced15f8166f86b264681efaaf6da5a8718e8425b70181d49425a6c

Tx prefix hash: 2f6448d9aef921b7d8262754ecf49e8cd72ca58bd8a3adb18770d52831426f1e
Tx public key: eb4ea9afde9eaecfe1f021447f16bd37379b2e79e5b171e3bacffe7214bdae28
Timestamp: 1734386572 Timestamp [UCT]: 2024-12-16 22:02:52 Age [y:d:h:m:s]: 00:024:09:24:35
Block: 1176735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17423 RingCT/type: yes/0
Extra: 01eb4ea9afde9eaecfe1f021447f16bd37379b2e79e5b171e3bacffe7214bdae280211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd6f0ce07b0a550d714d920573c4417c04603cd51f91cc983e08d0d512d9ba61 0.600000000000 1663094 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": 1176745, "vin": [ { "gen": { "height": 1176735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd6f0ce07b0a550d714d920573c4417c04603cd51f91cc983e08d0d512d9ba61" } } ], "extra": [ 1, 235, 78, 169, 175, 222, 158, 174, 207, 225, 240, 33, 68, 127, 22, 189, 55, 55, 155, 46, 121, 229, 177, 113, 227, 186, 207, 254, 114, 20, 189, 174, 40, 2, 17, 0, 0, 0, 6, 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