Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 801d53c8c3ee96d8e09c3f32092f018f0803db098e465fec7880867dfbc906cb

Tx prefix hash: c582fe9677d967aa2c3f9a2ac982815dfd3d2e50610037a82d05b8b3b80b4b6f
Tx public key: aadbc3e495fed7f48211197796744381a8f2f84afcb6a9ef7ac390a022a388ca
Timestamp: 1734049527 Timestamp [UCT]: 2024-12-13 00:25:27 Age [y:d:h:m:s]: 00:096:14:50:56
Block: 1173943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68841 RingCT/type: yes/0
Extra: 01aadbc3e495fed7f48211197796744381a8f2f84afcb6a9ef7ac390a022a388ca0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31e02698151327c291f9e472e9757f6fd94610cfe7a33242691c3832a8aae83b 0.600000000000 1660034 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": 1173953, "vin": [ { "gen": { "height": 1173943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31e02698151327c291f9e472e9757f6fd94610cfe7a33242691c3832a8aae83b" } } ], "extra": [ 1, 170, 219, 195, 228, 149, 254, 215, 244, 130, 17, 25, 119, 150, 116, 67, 129, 168, 242, 248, 74, 252, 182, 169, 239, 122, 195, 144, 160, 34, 163, 136, 202, 2, 17, 0, 0, 0, 4, 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