Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9553de2563fade3f744c57dd3eb48a574b55b019dbd494cb534aa990ea8578c6

Tx prefix hash: e7062cad7e27360a6f083e707ccaa6cc18235b62d900348a3a768194e3aa12c4
Tx public key: 735f6248f7a5a6e87525dce0c6af5006b916a737867b1277ddb7a5a595901cbe
Timestamp: 1705474501 Timestamp [UCT]: 2024-01-17 06:55:01 Age [y:d:h:m:s]: 01:296:01:02:39
Block: 937114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470401 RingCT/type: yes/0
Extra: 01735f6248f7a5a6e87525dce0c6af5006b916a737867b1277ddb7a5a595901cbe02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f90ee7e1674ef157ec9964a6a911321d2dc51377892c7c0214a1d29d8f78972e 0.600000000000 1395158 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": 937124, "vin": [ { "gen": { "height": 937114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f90ee7e1674ef157ec9964a6a911321d2dc51377892c7c0214a1d29d8f78972e" } } ], "extra": [ 1, 115, 95, 98, 72, 247, 165, 166, 232, 117, 37, 220, 224, 198, 175, 80, 6, 185, 22, 167, 55, 134, 123, 18, 119, 221, 183, 165, 165, 149, 144, 28, 190, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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