Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ea3937bedc929b319725ad4beb4a23c64ce7d50de7a045c74d4ffcd26ddf82

Tx prefix hash: 29acd8b962bbd1ba8aadb09a8afa759a941f05aecfa4df0ccc4d69493ba5c483
Tx public key: ae8f3ea0fa29097ee4fd5a3440dc0752e31c869bddff6969cdd17dc17a64e645
Timestamp: 1740303398 Timestamp [UCT]: 2025-02-23 09:36:38 Age [y:d:h:m:s]: 00:227:13:06:36
Block: 1225413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160334 RingCT/type: yes/0
Extra: 01ae8f3ea0fa29097ee4fd5a3440dc0752e31c869bddff6969cdd17dc17a64e645021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bed4c6778f0b4c336935b873807d710679205efa148aa31008d05163e6eb5908 0.600000000000 1712278 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": 1225423, "vin": [ { "gen": { "height": 1225413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bed4c6778f0b4c336935b873807d710679205efa148aa31008d05163e6eb5908" } } ], "extra": [ 1, 174, 143, 62, 160, 250, 41, 9, 126, 228, 253, 90, 52, 64, 220, 7, 82, 227, 28, 134, 155, 221, 255, 105, 105, 205, 209, 125, 193, 122, 100, 230, 69, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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