Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7da63db15079343e556607ca8c235cc868153f890e5b59d1a52616b88b9aafb

Tx prefix hash: 4b24eba9485e6e783526168c765b6e34b84d430b623c1818cabc617182831ca3
Tx public key: 27579bff5a2d58b617c8ddff20aa4b2c4f62b0218d33165e7e55eaaed2580157
Timestamp: 1715174471 Timestamp [UCT]: 2024-05-08 13:21:11 Age [y:d:h:m:s]: 01:240:20:18:22
Block: 1017560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430834 RingCT/type: yes/0
Extra: 0127579bff5a2d58b617c8ddff20aa4b2c4f62b0218d33165e7e55eaaed25801570211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b1f5fd447f75f79fa5e8d85d357ede193b0a19c7e8e95143093ee12cf5ccaa 0.600000000000 1481343 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": 1017570, "vin": [ { "gen": { "height": 1017560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b1f5fd447f75f79fa5e8d85d357ede193b0a19c7e8e95143093ee12cf5ccaa" } } ], "extra": [ 1, 39, 87, 155, 255, 90, 45, 88, 182, 23, 200, 221, 255, 32, 170, 75, 44, 79, 98, 176, 33, 141, 51, 22, 94, 126, 85, 234, 174, 210, 88, 1, 87, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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