Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49574d043f7f45deb3e2ed9cc0a0e7d7bac1ec20226d0dd188b4ede506b31383

Tx prefix hash: cfbb7ccd9125f425850f56949a8cccf14da41cc9cc0f0ea3971e257ab0e009b1
Tx public key: aeaf5e298d1ef497286e82bf46b1e26a2a40313db43c1a279c14d8c85ceecf51
Timestamp: 1744139681 Timestamp [UCT]: 2025-04-08 19:14:41 Age [y:d:h:m:s]: 00:274:13:15:30
Block: 1257176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194037 RingCT/type: yes/0
Extra: 01aeaf5e298d1ef497286e82bf46b1e26a2a40313db43c1a279c14d8c85ceecf510211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 624c062f950017ffb22040fac3c0e0a5b0c379b4cb936d76088b4e06bd5051ca 0.600000000000 1744295 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": 1257186, "vin": [ { "gen": { "height": 1257176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "624c062f950017ffb22040fac3c0e0a5b0c379b4cb936d76088b4e06bd5051ca" } } ], "extra": [ 1, 174, 175, 94, 41, 141, 30, 244, 151, 40, 110, 130, 191, 70, 177, 226, 106, 42, 64, 49, 61, 180, 60, 26, 39, 156, 20, 216, 200, 92, 238, 207, 81, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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