Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1444ae5976e3329eb62059542ca89edc817b0d185044e7bc9f7246598a23873b

Tx prefix hash: 869f141d9ef9b88d2f36d80fda392092cfe7a8a30c9e86dce199dd1c5d5eedb1
Tx public key: be2f4c7d3db08dc5b4d9080a880128637f64d3ebebf6af353c0c12b421fa43d0
Timestamp: 1708782119 Timestamp [UCT]: 2024-02-24 13:41:59 Age [y:d:h:m:s]: 01:043:16:37:57
Block: 964555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292234 RingCT/type: yes/0
Extra: 01be2f4c7d3db08dc5b4d9080a880128637f64d3ebebf6af353c0c12b421fa43d002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ffad225b23acd9c6018320ab4ec96b7b0d888075643bb566b2a2791802280b4 0.600000000000 1424296 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": 964565, "vin": [ { "gen": { "height": 964555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ffad225b23acd9c6018320ab4ec96b7b0d888075643bb566b2a2791802280b4" } } ], "extra": [ 1, 190, 47, 76, 125, 61, 176, 141, 197, 180, 217, 8, 10, 136, 1, 40, 99, 127, 100, 211, 235, 235, 246, 175, 53, 60, 12, 18, 180, 33, 250, 67, 208, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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