Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eae3e999874041a2aab560aa286a2387e3af0b0449573932f4e1bfc78d7aa477

Tx prefix hash: 86531eddab8390f44d2b6bc78ebc6c2dc119b19189e1b4aa6cb5e1d412a0c0b1
Tx public key: e20083363fc4c3255f58b6f6a464b7d9919e46dd792d05023fa5eb955ab80d6b
Timestamp: 1703653027 Timestamp [UCT]: 2023-12-27 04:57:07 Age [y:d:h:m:s]: 01:319:20:11:15
Block: 922023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487429 RingCT/type: yes/0
Extra: 01e20083363fc4c3255f58b6f6a464b7d9919e46dd792d05023fa5eb955ab80d6b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131a5f07ee7d3df492e29b445d2aca63107b2fc2619f0cd8ffc0da287f56d05a 0.600000000000 1379717 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": 922033, "vin": [ { "gen": { "height": 922023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131a5f07ee7d3df492e29b445d2aca63107b2fc2619f0cd8ffc0da287f56d05a" } } ], "extra": [ 1, 226, 0, 131, 54, 63, 196, 195, 37, 95, 88, 182, 246, 164, 100, 183, 217, 145, 158, 70, 221, 121, 45, 5, 2, 63, 165, 235, 149, 90, 184, 13, 107, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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