Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 046657e49843f40f2b85331bae7ab0d52a85c2fc2217302060d1431e099ccd81

Tx prefix hash: 89b16f486445bb1e30a1c9a651d1f70ac6e54f21537a1d9ae7d3b2070adec461
Tx public key: 346c1992db98fa3f21230024faec0e786e3a4058ad8cd2c0f24674a1203ddcfa
Timestamp: 1696097609 Timestamp [UCT]: 2023-09-30 18:13:29 Age [y:d:h:m:s]: 02:039:19:58:46
Block: 859595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548102 RingCT/type: yes/0
Extra: 01346c1992db98fa3f21230024faec0e786e3a4058ad8cd2c0f24674a1203ddcfa0211000000054b8f5122000000000000000000

1 output(s) for total of 0.870572557000 dcy

stealth address amount amount idx
00: 8dc181d23e7ef885212e2a55d6153160ec5f059fb397120ca543a2402d09e8bb 0.870572557000 1313827 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": 859605, "vin": [ { "gen": { "height": 859595 } } ], "vout": [ { "amount": 870572557, "target": { "key": "8dc181d23e7ef885212e2a55d6153160ec5f059fb397120ca543a2402d09e8bb" } } ], "extra": [ 1, 52, 108, 25, 146, 219, 152, 250, 63, 33, 35, 0, 36, 250, 236, 14, 120, 110, 58, 64, 88, 173, 140, 210, 192, 242, 70, 116, 161, 32, 61, 220, 250, 2, 17, 0, 0, 0, 5, 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