Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84570e4583092f17921f7804bc1e3e35eff252e548e2165ef9b9f2c1e25932a3

Tx prefix hash: b76c0c423ef799ae8d3598caf828f0e73e27b64c81c5eefd3c8f7b5bf24c49ab
Tx public key: bf7e6610e0e8acccddf6ce2c3f1e2df6e4a1e0b8434d8a54d5c91f39634f4ebc
Timestamp: 1681928037 Timestamp [UCT]: 2023-04-19 18:13:57 Age [y:d:h:m:s]: 02:060:19:57:03
Block: 742164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565532 RingCT/type: yes/0
Extra: 01bf7e6610e0e8acccddf6ce2c3f1e2df6e4a1e0b8434d8a54d5c91f39634f4ebc02110000000375e3f0e9000000000000000000

1 output(s) for total of 2.132567546000 dcy

stealth address amount amount idx
00: 84dbc121697d77c506967ccef43516dc5be3343a210daec482765e22cb127156 2.132567546000 1189123 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": 742174, "vin": [ { "gen": { "height": 742164 } } ], "vout": [ { "amount": 2132567546, "target": { "key": "84dbc121697d77c506967ccef43516dc5be3343a210daec482765e22cb127156" } } ], "extra": [ 1, 191, 126, 102, 16, 224, 232, 172, 204, 221, 246, 206, 44, 63, 30, 45, 246, 228, 161, 224, 184, 67, 77, 138, 84, 213, 201, 31, 57, 99, 79, 78, 188, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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