Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8f171526f9f794862c655eb20213c829b1270e91d776304226cde38e3460ff

Tx prefix hash: 6c2e91c35911b0bbdabcb801275470de69e3be8aa914e0b691d1737615bfa2ba
Tx public key: 25cda47f55b6bd340702597e4d1a9ce4a93f4fc1f9a7070f90c57857e700e1cd
Timestamp: 1703365470 Timestamp [UCT]: 2023-12-23 21:04:30 Age [y:d:h:m:s]: 01:101:06:31:26
Block: 919646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333484 RingCT/type: yes/0
Extra: 0125cda47f55b6bd340702597e4d1a9ce4a93f4fc1f9a7070f90c57857e700e1cd02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3622309e73f12a2d59bf851cdc15699f758871d9cc94998f1e8264c86eac6d1d 0.600000000000 1377322 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": 919656, "vin": [ { "gen": { "height": 919646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3622309e73f12a2d59bf851cdc15699f758871d9cc94998f1e8264c86eac6d1d" } } ], "extra": [ 1, 37, 205, 164, 127, 85, 182, 189, 52, 7, 2, 89, 126, 77, 26, 156, 228, 169, 63, 79, 193, 249, 167, 7, 15, 144, 197, 120, 87, 231, 0, 225, 205, 2, 17, 0, 0, 0, 10, 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