Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e4f2b1721844669c048f45b126c2241970fd20d5759c009424d14b38066f30

Tx prefix hash: 673eb374f8b57a882d2b9d12970da8202c610ea7d62756ea15743580b624fcf6
Tx public key: 0f79cbe36d8d9ce8bf1081cdc36fe7a6f82b9a20b95ecf063e72b653d01f9a27
Timestamp: 1697104745 Timestamp [UCT]: 2023-10-12 09:59:05 Age [y:d:h:m:s]: 01:100:01:21:35
Block: 867959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332719 RingCT/type: yes/0
Extra: 010f79cbe36d8d9ce8bf1081cdc36fe7a6f82b9a20b95ecf063e72b653d01f9a2702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.816754538000 dcy

stealth address amount amount idx
00: dd0ffe67c3b3e2f375002a119c4dcee9ba7e9fbb367a580d3c4c7537c92ad0de 0.816754538000 1322702 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": 867969, "vin": [ { "gen": { "height": 867959 } } ], "vout": [ { "amount": 816754538, "target": { "key": "dd0ffe67c3b3e2f375002a119c4dcee9ba7e9fbb367a580d3c4c7537c92ad0de" } } ], "extra": [ 1, 15, 121, 203, 227, 109, 141, 156, 232, 191, 16, 129, 205, 195, 111, 231, 166, 248, 43, 154, 32, 185, 94, 207, 6, 62, 114, 182, 83, 208, 31, 154, 39, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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