Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b9bd2c515fceb56b52993399627d56de7edbabc3f8d8db579a20945bebf68c

Tx prefix hash: c18701644adffe2f6af2e4987d8f9cd2cbe79a9df3a33f4a5f2d4c7984979253
Tx public key: ddf01d21d31280bb99d3235b8ef00a0e5c357a5456cd2cf5861b33a02d40f844
Timestamp: 1702187464 Timestamp [UCT]: 2023-12-10 05:51:04 Age [y:d:h:m:s]: 01:158:04:43:38
Block: 909885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374220 RingCT/type: yes/0
Extra: 01ddf01d21d31280bb99d3235b8ef00a0e5c357a5456cd2cf5861b33a02d40f8440211000000024b8f5122000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: bba91363d3f2b60e39a043c663e2eccd87ea80bc381cfca5f8ae296a2bf86e65 0.600010000000 1367012 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": 909895, "vin": [ { "gen": { "height": 909885 } } ], "vout": [ { "amount": 600010000, "target": { "key": "bba91363d3f2b60e39a043c663e2eccd87ea80bc381cfca5f8ae296a2bf86e65" } } ], "extra": [ 1, 221, 240, 29, 33, 211, 18, 128, 187, 153, 211, 35, 91, 142, 240, 10, 14, 92, 53, 122, 84, 86, 205, 44, 245, 134, 27, 51, 160, 45, 64, 248, 68, 2, 17, 0, 0, 0, 2, 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