Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe032e581a62e45bb518ef2e758231c333d53410fea3c145a7b6cf000fbfabc

Tx prefix hash: f702616a254f2614dd90da687d2f46894ce934d5935464dc3892e0cb6021795f
Tx public key: e0000b7bbf5ebbac2a2e5730f87319adcc0145b14c4ba4f2fd01990714f0cc1e
Timestamp: 1719003790 Timestamp [UCT]: 2024-06-21 21:03:10 Age [y:d:h:m:s]: 00:270:14:34:21
Block: 1049272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193402 RingCT/type: yes/0
Extra: 01e0000b7bbf5ebbac2a2e5730f87319adcc0145b14c4ba4f2fd01990714f0cc1e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a92ff2cab016897d9f380ea0fd02523f37691fb572414d0bca80bd0bb246a601 0.600000000000 1519371 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": 1049282, "vin": [ { "gen": { "height": 1049272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a92ff2cab016897d9f380ea0fd02523f37691fb572414d0bca80bd0bb246a601" } } ], "extra": [ 1, 224, 0, 11, 123, 191, 94, 187, 172, 42, 46, 87, 48, 248, 115, 25, 173, 204, 1, 69, 177, 76, 75, 164, 242, 253, 1, 153, 7, 20, 240, 204, 30, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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