Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81fded690317648a0c44c978fadce11609e470a3c61a5be5bdf6b04ab514f03a

Tx prefix hash: 8e84bd41a4a2a3cd8f9cef8957f0816a7ee607bdd8cb128d60359f18fb11f048
Tx public key: ad879a746131d341e0cece8ee8659e7ed75916ccb6331a9d6803e9ccf5a43a57
Timestamp: 1710291233 Timestamp [UCT]: 2024-03-13 00:53:53 Age [y:d:h:m:s]: 00:349:11:11:19
Block: 977073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249847 RingCT/type: yes/0
Extra: 01ad879a746131d341e0cece8ee8659e7ed75916ccb6331a9d6803e9ccf5a43a570211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acd1c7181fdf6f01a79084bfc77599609d30a866eeed0ba6aa99a73218e40d17 0.600000000000 1437074 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": 977083, "vin": [ { "gen": { "height": 977073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acd1c7181fdf6f01a79084bfc77599609d30a866eeed0ba6aa99a73218e40d17" } } ], "extra": [ 1, 173, 135, 154, 116, 97, 49, 211, 65, 224, 206, 206, 142, 232, 101, 158, 126, 215, 89, 22, 204, 182, 51, 26, 157, 104, 3, 233, 204, 245, 164, 58, 87, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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