Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9748aeea3dbbeff76bc642520afb24a1524052238dae66a7510b611085e3c0ba

Tx prefix hash: c76eb7a5195385e946daafd313d9efa3dc251a09792d7018f226dd7a445f37c6
Tx public key: b5714269a7c626471c401649ea9958bcb3bc9ac8fd76ad5eae41fb62b8598cc6
Timestamp: 1728381814 Timestamp [UCT]: 2024-10-08 10:03:34 Age [y:d:h:m:s]: 01:034:09:53:46
Block: 1127043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282976 RingCT/type: yes/0
Extra: 01b5714269a7c626471c401649ea9958bcb3bc9ac8fd76ad5eae41fb62b8598cc6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a021d7a98e138346611f7910af661cf1d75055399b2bb91ea5cd1d2f880262d 0.600000000000 1609842 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": 1127053, "vin": [ { "gen": { "height": 1127043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a021d7a98e138346611f7910af661cf1d75055399b2bb91ea5cd1d2f880262d" } } ], "extra": [ 1, 181, 113, 66, 105, 167, 198, 38, 71, 28, 64, 22, 73, 234, 153, 88, 188, 179, 188, 154, 200, 253, 118, 173, 94, 174, 65, 251, 98, 184, 89, 140, 198, 2, 17, 0, 0, 0, 5, 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