Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05519a4d52de21e3a55120ad1af1c67214ad168aeb4edae17753b6c7bae800e7

Tx prefix hash: 72b88416b52cebaeda4b64b584a7b87a7941435cccb7578f3dc8311e6942ee26
Tx public key: fc71bfae8c4a323dd2296cdbcd5cd3fd72e75f53dabbeb059ec866635a344311
Timestamp: 1720951335 Timestamp [UCT]: 2024-07-14 10:02:15 Age [y:d:h:m:s]: 00:269:18:25:34
Block: 1065456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192720 RingCT/type: yes/0
Extra: 01fc71bfae8c4a323dd2296cdbcd5cd3fd72e75f53dabbeb059ec866635a34431102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d47a8231d7d079268d5b9c2c532bd5bc1a3b79ecb85b08808d2e992b90796ae7 0.600000000000 1536001 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": 1065466, "vin": [ { "gen": { "height": 1065456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d47a8231d7d079268d5b9c2c532bd5bc1a3b79ecb85b08808d2e992b90796ae7" } } ], "extra": [ 1, 252, 113, 191, 174, 140, 74, 50, 61, 210, 41, 108, 219, 205, 92, 211, 253, 114, 231, 95, 83, 218, 187, 235, 5, 158, 200, 102, 99, 90, 52, 67, 17, 2, 17, 0, 0, 0, 8, 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