Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4fbb3ac432424d51d437a21c8f95e3a12b2431b1a132018e0ac422ccb7f519

Tx prefix hash: 05e561d66c48755fb89f1cc45e9d7a9e503f10841b20dc4d6bd872618ce3c593
Tx public key: 4882d0be1beedb8ab85c2192e6efc0d116342aa104b6d597c80aadb3a369dd47
Timestamp: 1710348006 Timestamp [UCT]: 2024-03-13 16:40:06 Age [y:d:h:m:s]: 01:252:11:36:47
Block: 977552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439145 RingCT/type: yes/0
Extra: 014882d0be1beedb8ab85c2192e6efc0d116342aa104b6d597c80aadb3a369dd4702110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b88f4da01489fd46600b046ef7b1d48e3dfd81a60734fc4f2c65ee076b7dd3 0.600000000000 1437555 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": 977562, "vin": [ { "gen": { "height": 977552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b88f4da01489fd46600b046ef7b1d48e3dfd81a60734fc4f2c65ee076b7dd3" } } ], "extra": [ 1, 72, 130, 208, 190, 27, 238, 219, 138, 184, 92, 33, 146, 230, 239, 192, 209, 22, 52, 42, 161, 4, 182, 213, 151, 200, 10, 173, 179, 163, 105, 221, 71, 2, 17, 0, 0, 0, 5, 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