Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6460c1d546b9f6744c6a71bf8b7e943abb6b47f5fe753753d683704712f133

Tx prefix hash: 43716d706784c4e69dce29127f25d5edaec2c8d4bc293514abcd6c7f2a6c15ce
Tx public key: 490ade7a545afc67e23d1f9986bb36fb3a5001f03deec2a85f3289bf364d05fb
Timestamp: 1730756902 Timestamp [UCT]: 2024-11-04 21:48:22 Age [y:d:h:m:s]: 00:219:03:47:29
Block: 1146644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156485 RingCT/type: yes/0
Extra: 01490ade7a545afc67e23d1f9986bb36fb3a5001f03deec2a85f3289bf364d05fb0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff4a346840ee898736adf85b511af3bb13b283347d17ea59a9534ddd3cab04f4 0.600000000000 1631335 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": 1146654, "vin": [ { "gen": { "height": 1146644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff4a346840ee898736adf85b511af3bb13b283347d17ea59a9534ddd3cab04f4" } } ], "extra": [ 1, 73, 10, 222, 122, 84, 90, 252, 103, 226, 61, 31, 153, 134, 187, 54, 251, 58, 80, 1, 240, 61, 238, 194, 168, 95, 50, 137, 191, 54, 77, 5, 251, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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