Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3516b56c9519be2d5003885524c1f1f1461879c1ec399ad9e7d3f37ac3a5d7b6

Tx prefix hash: e42786c60cc83fd5ed4cbf434366a685c1c10c55ee4b67c252eccdb0836231f2
Tx public key: 49f564a4fa0fda6104b770d966315a49973446c88e164a1c7af77134568ff9e4
Timestamp: 1696806963 Timestamp [UCT]: 2023-10-08 23:16:03 Age [y:d:h:m:s]: 01:176:15:23:19
Block: 865484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387280 RingCT/type: yes/0
Extra: 0149f564a4fa0fda6104b770d966315a49973446c88e164a1c7af77134568ff9e40211000000014b8f5122000000000000000000

1 output(s) for total of 0.832323703000 dcy

stealth address amount amount idx
00: 6f227b9b30a44a886a3de920a2b451d9eb17c3cd3b1eec43b06fe0324d8ec609 0.832323703000 1320020 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": 865494, "vin": [ { "gen": { "height": 865484 } } ], "vout": [ { "amount": 832323703, "target": { "key": "6f227b9b30a44a886a3de920a2b451d9eb17c3cd3b1eec43b06fe0324d8ec609" } } ], "extra": [ 1, 73, 245, 100, 164, 250, 15, 218, 97, 4, 183, 112, 217, 102, 49, 90, 73, 151, 52, 70, 200, 142, 22, 74, 28, 122, 247, 113, 52, 86, 143, 249, 228, 2, 17, 0, 0, 0, 1, 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