Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7aab4e5f1c9221b2f1e6fa398f80b52818e4ea8ce55c3eea0623bed3ccf6675

Tx prefix hash: 53fb3950e11f9bb4b383effd9d080faf03cabef2262201835440947aa387029a
Tx public key: 5570b379cefbb3e4c3991cd3113ead40bb7cbeea47333138ce4fb3044fb2dba1
Timestamp: 1698404459 Timestamp [UCT]: 2023-10-27 11:00:59 Age [y:d:h:m:s]: 01:088:09:03:39
Block: 878737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324345 RingCT/type: yes/0
Extra: 015570b379cefbb3e4c3991cd3113ead40bb7cbeea47333138ce4fb3044fb2dba10211000000064b8f5122000000000000000000

1 output(s) for total of 0.752280063000 dcy

stealth address amount amount idx
00: 6a6840706020bda2c44f88a9e702d3e8c4a45ac094a09ad43faf8a3b17e1da68 0.752280063000 1334211 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": 878747, "vin": [ { "gen": { "height": 878737 } } ], "vout": [ { "amount": 752280063, "target": { "key": "6a6840706020bda2c44f88a9e702d3e8c4a45ac094a09ad43faf8a3b17e1da68" } } ], "extra": [ 1, 85, 112, 179, 121, 206, 251, 179, 228, 195, 153, 28, 211, 17, 62, 173, 64, 187, 124, 190, 234, 71, 51, 49, 56, 206, 79, 179, 4, 79, 178, 219, 161, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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