Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e842ad4751872eb9b1cedbf640eca1af6a800ae74ed5a7d37c8f47f7cacf943a

Tx prefix hash: 07688877d8373aad7abda2a75cb384cf0904df8ffb23de9f4b2b15ef369bd015
Tx public key: 0178a5a32f7e0385acf79d3c2f513e1e50d4c5228db860902f9e80f4d30edadd
Timestamp: 1662133212 Timestamp [UCT]: 2022-09-02 15:40:12 Age [y:d:h:m:s]: 02:129:10:02:20
Block: 579305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 613972 RingCT/type: yes/0
Extra: 010178a5a32f7e0385acf79d3c2f513e1e50d4c5228db860902f9e80f4d30edadd02110000000233af99f4000000000000000000

1 output(s) for total of 7.387919308000 dcy

stealth address amount amount idx
00: 32f144e454faa43218dfbf84553da123c8e31e4034067d12dac9b95b6061676a 7.387919308000 1012747 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": 579315, "vin": [ { "gen": { "height": 579305 } } ], "vout": [ { "amount": 7387919308, "target": { "key": "32f144e454faa43218dfbf84553da123c8e31e4034067d12dac9b95b6061676a" } } ], "extra": [ 1, 1, 120, 165, 163, 47, 126, 3, 133, 172, 247, 157, 60, 47, 81, 62, 30, 80, 212, 197, 34, 141, 184, 96, 144, 47, 158, 128, 244, 211, 14, 218, 221, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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