Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1cf0fdff473806784e68d841f3a831c3250d482b1a741c7ecd1b74d6042f598

Tx prefix hash: d2878e2f4a9c12ba0eff67f2908c2b179888dc93011b7338a1df438770a2b8b2
Tx public key: 9e718714f2ebcdf4e5c0536437340c4042ef8732a34134ba5fe521c4f841edac
Timestamp: 1698377517 Timestamp [UCT]: 2023-10-27 03:31:57 Age [y:d:h:m:s]: 01:180:23:57:55
Block: 878514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390366 RingCT/type: yes/0
Extra: 019e718714f2ebcdf4e5c0536437340c4042ef8732a34134ba5fe521c4f841edac0211000000034b8f5122000000000000000000

1 output(s) for total of 0.753561053000 dcy

stealth address amount amount idx
00: d4197ebda6e2a8f8413889c23be8ec7cb54a039777142e20ce1cceac96730155 0.753561053000 1333964 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": 878524, "vin": [ { "gen": { "height": 878514 } } ], "vout": [ { "amount": 753561053, "target": { "key": "d4197ebda6e2a8f8413889c23be8ec7cb54a039777142e20ce1cceac96730155" } } ], "extra": [ 1, 158, 113, 135, 20, 242, 235, 205, 244, 229, 192, 83, 100, 55, 52, 12, 64, 66, 239, 135, 50, 163, 65, 52, 186, 95, 229, 33, 196, 248, 65, 237, 172, 2, 17, 0, 0, 0, 3, 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