Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3799fbad89bad78fc1f805a4dd0d20a31e4c53eda019eb4e855640e944f12fa

Tx prefix hash: a37117d05fc950bc4b94c345285843a5ac2aec8dedf918b607314d29603dcb3c
Tx public key: 637cbd0d4e0c899bfeb246d62fa5c54c97945faead99a54d9ba4b2bf78c49f5b
Timestamp: 1711263294 Timestamp [UCT]: 2024-03-24 06:54:54 Age [y:d:h:m:s]: 01:081:23:48:52
Block: 985146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319521 RingCT/type: yes/0
Extra: 01637cbd0d4e0c899bfeb246d62fa5c54c97945faead99a54d9ba4b2bf78c49f5b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 735022245c6c068df1a9f17cb9f0b9bd831b27e6902ef09b97749d5ede4a1047 0.600000000000 1445353 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": 985156, "vin": [ { "gen": { "height": 985146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "735022245c6c068df1a9f17cb9f0b9bd831b27e6902ef09b97749d5ede4a1047" } } ], "extra": [ 1, 99, 124, 189, 13, 78, 12, 137, 155, 254, 178, 70, 214, 47, 165, 197, 76, 151, 148, 95, 174, 173, 153, 165, 77, 155, 164, 178, 191, 120, 196, 159, 91, 2, 17, 0, 0, 0, 3, 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