Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9c5ca541b67841f1e634f624d8aebfa0585f7e3b27cda619c576d6f63f9aace

Tx prefix hash: cd56a094107e9bddbf1e57c16b31b82b4795e5273007a1270e78249b28019cc0
Tx public key: 1e0edd1efbf01e24a0c12a4987af13d3e5292db645ac84080fcea0fa83dd96da
Timestamp: 1702261281 Timestamp [UCT]: 2023-12-11 02:21:21 Age [y:d:h:m:s]: 01:048:17:23:02
Block: 910491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295945 RingCT/type: yes/0
Extra: 011e0edd1efbf01e24a0c12a4987af13d3e5292db645ac84080fcea0fa83dd96da021100000010faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec39932a4843d2835485ead98c649cc28402be9a4cafd0ee5f9c834375b8d0e7 0.600000000000 1367652 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": 910501, "vin": [ { "gen": { "height": 910491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec39932a4843d2835485ead98c649cc28402be9a4cafd0ee5f9c834375b8d0e7" } } ], "extra": [ 1, 30, 14, 221, 30, 251, 240, 30, 36, 160, 193, 42, 73, 135, 175, 19, 211, 229, 41, 45, 182, 69, 172, 132, 8, 15, 206, 160, 250, 131, 221, 150, 218, 2, 17, 0, 0, 0, 16, 250, 243, 92, 156, 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