Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eabeba13ffa916aad6b8b23d24f381f6019d5ae3778de1c5fc08e587e8cef9e3

Tx prefix hash: fd17757181ad6d09e54b6d12811192f7e677f5f7b48e10760ad0c5829733e27c
Tx public key: 803cfa9b96583f0b8435bee77bbd0a5016e62a5efaf292cc90dc98edd915b9e6
Timestamp: 1704713700 Timestamp [UCT]: 2024-01-08 11:35:00 Age [y:d:h:m:s]: 01:088:07:10:07
Block: 930808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324218 RingCT/type: yes/0
Extra: 01803cfa9b96583f0b8435bee77bbd0a5016e62a5efaf292cc90dc98edd915b9e602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 983bad3897e865329b0a7fd760845a9e4bf65dd2efa4eeec35e78d20f6cb5968 0.600000000000 1388698 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": 930818, "vin": [ { "gen": { "height": 930808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "983bad3897e865329b0a7fd760845a9e4bf65dd2efa4eeec35e78d20f6cb5968" } } ], "extra": [ 1, 128, 60, 250, 155, 150, 88, 63, 11, 132, 53, 190, 231, 123, 189, 10, 80, 22, 230, 42, 94, 250, 242, 146, 204, 144, 220, 152, 237, 217, 21, 185, 230, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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