Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 528038e926f184b8a440f3842bb045b8f8d0be828b6902eb36d3944f128d1e04

Tx prefix hash: b540495e7cf47c5ab0bc3649c8117fbe3cce081b4cd94b96252c60b391429b86
Tx public key: 228d4818fbe8e8838fa3b917d601fa3e633f92b211bb6fdee4c37942f17c9c67
Timestamp: 1657135056 Timestamp [UCT]: 2022-07-06 19:17:36 Age [y:d:h:m:s]: 02:223:03:03:50
Block: 538070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 680592 RingCT/type: yes/0
Extra: 01228d4818fbe8e8838fa3b917d601fa3e633f92b211bb6fdee4c37942f17c9c670211000000014da16a3a000000000000000000

1 output(s) for total of 10.119309435000 dcy

stealth address amount amount idx
00: a115319ad603023973b2d5a12ea0279ddf9e3e0304763e49e1d2b1d2af555660 10.119309435000 968027 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": 538080, "vin": [ { "gen": { "height": 538070 } } ], "vout": [ { "amount": 10119309435, "target": { "key": "a115319ad603023973b2d5a12ea0279ddf9e3e0304763e49e1d2b1d2af555660" } } ], "extra": [ 1, 34, 141, 72, 24, 251, 232, 232, 131, 143, 163, 185, 23, 214, 1, 250, 62, 99, 63, 146, 178, 17, 187, 111, 222, 228, 195, 121, 66, 241, 124, 156, 103, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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