Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bda97b56fa5b0ca01e0ce9dd4130b9e394729ac9d4cd5e3f85dab0afb1498db

Tx prefix hash: 10a456c4992b7a0490573c14839af25c5d8fa232b595676a7afef2c46e89cdd0
Tx public key: ada245720e89f8f5c31a6b16c4477301aa318f03b54077dc49b7945678adbdc6
Timestamp: 1728957482 Timestamp [UCT]: 2024-10-15 01:58:02 Age [y:d:h:m:s]: 00:149:09:19:09
Block: 1131818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106554 RingCT/type: yes/0
Extra: 01ada245720e89f8f5c31a6b16c4477301aa318f03b54077dc49b7945678adbdc6021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fefa1c367e7815c90882724d639e8f716dfdbec6af942753d79f271f98064d1a 0.600000000000 1614725 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": 1131828, "vin": [ { "gen": { "height": 1131818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fefa1c367e7815c90882724d639e8f716dfdbec6af942753d79f271f98064d1a" } } ], "extra": [ 1, 173, 162, 69, 114, 14, 137, 248, 245, 195, 26, 107, 22, 196, 71, 115, 1, 170, 49, 143, 3, 181, 64, 119, 220, 73, 183, 148, 86, 120, 173, 189, 198, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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