Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe95dc71bb5306015d5ca4ba07a717e0bbec2588c8579e96b8c34bba2c1ee9a9

Tx prefix hash: df9f774f8cf0c2264b2401aafc90329800280ad4a177a02a8f0cace6e6bc699a
Tx public key: 51d8316db8a154e0a527606bb5713dadf519c105be30ca37ff0f6ba2d68ce2bf
Timestamp: 1735404165 Timestamp [UCT]: 2024-12-28 16:42:45 Age [y:d:h:m:s]: 00:082:03:37:27
Block: 1185134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58517 RingCT/type: yes/0
Extra: 0151d8316db8a154e0a527606bb5713dadf519c105be30ca37ff0f6ba2d68ce2bf0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aabdf4a8c31e0fb7cb477977b4719e2657bd70f5856b833fae023f4f12a188e1 0.600000000000 1671599 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": 1185144, "vin": [ { "gen": { "height": 1185134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aabdf4a8c31e0fb7cb477977b4719e2657bd70f5856b833fae023f4f12a188e1" } } ], "extra": [ 1, 81, 216, 49, 109, 184, 161, 84, 224, 165, 39, 96, 107, 181, 113, 61, 173, 245, 25, 193, 5, 190, 48, 202, 55, 255, 15, 107, 162, 214, 140, 226, 191, 2, 17, 0, 0, 0, 2, 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