Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afbc37158e771fc03a2ca3e94b77fd9ccb1b55f2bcce7da75e355628a69639a6

Tx prefix hash: 3119d4f9658c3b1323d12394a0690efe97f7fa870631d32e66c1e4a319965196
Tx public key: eb8b5650f4341c2d168bf93fcdf40bfa32019de75b2b22f5f5838b779ddae6b3
Timestamp: 1697445099 Timestamp [UCT]: 2023-10-16 08:31:39 Age [y:d:h:m:s]: 01:178:03:28:33
Block: 870768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388361 RingCT/type: yes/0
Extra: 01eb8b5650f4341c2d168bf93fcdf40bfa32019de75b2b22f5f5838b779ddae6b302110000000775e3f0e9000000000000000000

1 output(s) for total of 0.799436861000 dcy

stealth address amount amount idx
00: 8be3234c1ebfd901867bb0ca08b39a0d1839519651b33e975048dc16324a04cd 0.799436861000 1325655 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": 870778, "vin": [ { "gen": { "height": 870768 } } ], "vout": [ { "amount": 799436861, "target": { "key": "8be3234c1ebfd901867bb0ca08b39a0d1839519651b33e975048dc16324a04cd" } } ], "extra": [ 1, 235, 139, 86, 80, 244, 52, 28, 45, 22, 139, 249, 63, 205, 244, 11, 250, 50, 1, 157, 231, 91, 43, 34, 245, 245, 131, 139, 119, 157, 218, 230, 179, 2, 17, 0, 0, 0, 7, 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