Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b893a59b35bc3647d0f101778935b04c55fd3121bb44f355b64c66d2b5ea2088

Tx prefix hash: e2f167ea189580832b8dfc878e01c86e04ed362f92b051b7385df428bd79e144
Tx public key: 0d5001495ce2d70f1cb3d05ea25ffcda08f904affe094a96434eef47393b1003
Timestamp: 1733943318 Timestamp [UCT]: 2024-12-11 18:55:18 Age [y:d:h:m:s]: 00:112:04:26:22
Block: 1173063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79943 RingCT/type: yes/0
Extra: 010d5001495ce2d70f1cb3d05ea25ffcda08f904affe094a96434eef47393b10030211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae1d1c44efbc70a06a234b39c56d238532f2ee1516470986bc7d3f3f32a5a42a 0.600000000000 1659040 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": 1173073, "vin": [ { "gen": { "height": 1173063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae1d1c44efbc70a06a234b39c56d238532f2ee1516470986bc7d3f3f32a5a42a" } } ], "extra": [ 1, 13, 80, 1, 73, 92, 226, 215, 15, 28, 179, 208, 94, 162, 95, 252, 218, 8, 249, 4, 175, 254, 9, 74, 150, 67, 78, 239, 71, 57, 59, 16, 3, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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