Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3e347e8f271d8c5716830653e89d302a1a85bcfb9ba5072f0eba5e4aad8a43d

Tx prefix hash: 5633393382aab65ea1e7142092a38cd463b320e4e998802e3b5690e90a59fe93
Tx public key: 80dc8cdd88b6c0988253a7db35bf646864e0dfb3cf678b759acef2e7c780395c
Timestamp: 1710816391 Timestamp [UCT]: 2024-03-19 02:46:31 Age [y:d:h:m:s]: 01:317:22:31:44
Block: 981439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485833 RingCT/type: yes/0
Extra: 0180dc8cdd88b6c0988253a7db35bf646864e0dfb3cf678b759acef2e7c780395c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0daf8f2e1069068acc3f45f4f8adfa14f51432f78742049b5311469af59d4d24 0.600000000000 1441534 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": 981449, "vin": [ { "gen": { "height": 981439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0daf8f2e1069068acc3f45f4f8adfa14f51432f78742049b5311469af59d4d24" } } ], "extra": [ 1, 128, 220, 140, 221, 136, 182, 192, 152, 130, 83, 167, 219, 53, 191, 100, 104, 100, 224, 223, 179, 207, 103, 139, 117, 154, 206, 242, 231, 199, 128, 57, 92, 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