Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979754a3c5e9caa8b40a60b8449174ee84956d667d8295eee086ff85e5609e9d

Tx prefix hash: 369eab47089b207edfc695561acdc1d64f831f0b7a3881bbef699b4f5cf5e53b
Tx public key: f32e1ee8fb8bfcb94b308d1fe3afb48c7520e8a55a22fb64e1cbb928f4f21fb5
Timestamp: 1723623678 Timestamp [UCT]: 2024-08-14 08:21:18 Age [y:d:h:m:s]: 01:098:16:03:04
Block: 1087605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328977 RingCT/type: yes/0
Extra: 01f32e1ee8fb8bfcb94b308d1fe3afb48c7520e8a55a22fb64e1cbb928f4f21fb5021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26a41926fe7d162afaae496d058b2d84a2139fc900f2fe87a5769420d2aa5d15 0.600000000000 1562214 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": 1087615, "vin": [ { "gen": { "height": 1087605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26a41926fe7d162afaae496d058b2d84a2139fc900f2fe87a5769420d2aa5d15" } } ], "extra": [ 1, 243, 46, 30, 232, 251, 139, 252, 185, 75, 48, 141, 31, 227, 175, 180, 140, 117, 32, 232, 165, 90, 34, 251, 100, 225, 203, 185, 40, 244, 242, 31, 181, 2, 17, 0, 0, 0, 6, 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