Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bef94f585a96877bf2640c1f2a133e4e5234fbb24c49c104a08f687f35d55cb

Tx prefix hash: 1819b7f219ed9df897a30a48c3cb161f6c47bb695a0bc148eadd157778803cae
Tx public key: e6f67a88a0408422b0e08bb6943b35e3668870cc25f7cbbdac3087d011c3eb04
Timestamp: 1715857172 Timestamp [UCT]: 2024-05-16 10:59:32 Age [y:d:h:m:s]: 00:362:07:33:55
Block: 1023204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259008 RingCT/type: yes/0
Extra: 01e6f67a88a0408422b0e08bb6943b35e3668870cc25f7cbbdac3087d011c3eb040211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 267c80b5098e9b406ccf3917aab2dfc4d5dd34373cc02ba41a6e20e439f6575c 0.600000000000 1488037 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": 1023214, "vin": [ { "gen": { "height": 1023204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "267c80b5098e9b406ccf3917aab2dfc4d5dd34373cc02ba41a6e20e439f6575c" } } ], "extra": [ 1, 230, 246, 122, 136, 160, 64, 132, 34, 176, 224, 139, 182, 148, 59, 53, 227, 102, 136, 112, 204, 37, 247, 203, 189, 172, 48, 135, 208, 17, 195, 235, 4, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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