Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56cd945cd9f5c23b955e4c58b91b9219ecc2a1fc3204ace4210403b04e458cf5

Tx prefix hash: 68f17f23bae97bab70ad1355a477845ebf2cf35e55999c86f375ceb44fb7b34c
Tx public key: 1b47a07d497b366d9d79e7651d1afb1a033d81aacdc21ff84baca13d045b48c1
Timestamp: 1720972810 Timestamp [UCT]: 2024-07-14 16:00:10 Age [y:d:h:m:s]: 00:274:16:16:56
Block: 1065629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196236 RingCT/type: yes/0
Extra: 011b47a07d497b366d9d79e7651d1afb1a033d81aacdc21ff84baca13d045b48c102110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5de41bf798b69c9dd753627f8caa6c872c05fb5ccf8b5e1aa50b66317ab0002 0.600000000000 1536178 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": 1065639, "vin": [ { "gen": { "height": 1065629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5de41bf798b69c9dd753627f8caa6c872c05fb5ccf8b5e1aa50b66317ab0002" } } ], "extra": [ 1, 27, 71, 160, 125, 73, 123, 54, 109, 157, 121, 231, 101, 29, 26, 251, 26, 3, 61, 129, 170, 205, 194, 31, 248, 75, 172, 161, 61, 4, 91, 72, 193, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 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