Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adea3a2561289f3cdaaedc59619309e7a928af682dee535e67bc178fec3e15bc

Tx prefix hash: 798906f5970325431e978004c6093887a463b4d4e0b58ec30e29c9490fed21d0
Tx public key: 5b1455ec7a0a1eadd572b1d7fb8382bb963fe6c5323751dc7c98a1c24ea1a722
Timestamp: 1711180284 Timestamp [UCT]: 2024-03-23 07:51:24 Age [y:d:h:m:s]: 01:086:18:17:09
Block: 984460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322890 RingCT/type: yes/0
Extra: 015b1455ec7a0a1eadd572b1d7fb8382bb963fe6c5323751dc7c98a1c24ea1a7220211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad59e14d8ba26098cacabaec72df50179f9e155cf7e3ce876e3f8ebb8299efa5 0.600000000000 1444631 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": 984470, "vin": [ { "gen": { "height": 984460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad59e14d8ba26098cacabaec72df50179f9e155cf7e3ce876e3f8ebb8299efa5" } } ], "extra": [ 1, 91, 20, 85, 236, 122, 10, 30, 173, 213, 114, 177, 215, 251, 131, 130, 187, 150, 63, 230, 197, 50, 55, 81, 220, 124, 152, 161, 194, 78, 161, 167, 34, 2, 17, 0, 0, 0, 2, 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