Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17e2168c7ed29af87f8a90547c08e60ab248276011f5053f8c631784e56d3a05

Tx prefix hash: 467d2a9f04c37adbb713013d3de3c0cf7a9b23d9d78c72286c428a11cc3f1192
Tx public key: 1e5cd35a85b579125a4752e9f58f0db6355b967e6c5387990c4945d89fc736c2
Timestamp: 1619533454 Timestamp [UCT]: 2021-04-27 14:24:14 Age [y:d:h:m:s]: 03:284:00:05:34
Block: 248973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 963008 RingCT/type: yes/0
Extra: 011e5cd35a85b579125a4752e9f58f0db6355b967e6c5387990c4945d89fc736c20211000000154405d762000000000000000000

1 output(s) for total of 91.843760661000 dcy

stealth address amount amount idx
00: 23f01ac3bce5e2ae3aa68bc245a4c532e6a2b955c17619942e9d5b628419de03 91.843760661000 521613 of 0

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": 248983, "vin": [ { "gen": { "height": 248973 } } ], "vout": [ { "amount": 91843760661, "target": { "key": "23f01ac3bce5e2ae3aa68bc245a4c532e6a2b955c17619942e9d5b628419de03" } } ], "extra": [ 1, 30, 92, 211, 90, 133, 181, 121, 18, 90, 71, 82, 233, 245, 143, 13, 182, 53, 91, 150, 126, 108, 83, 135, 153, 12, 73, 69, 216, 159, 199, 54, 194, 2, 17, 0, 0, 0, 21, 68, 5, 215, 98, 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