Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2597ba67b9b8c4ef1762208dba274f839b5f3b195f0902c33303aaa6e8bf0e8

Tx prefix hash: 3ba88a99b8072673dcf48d714e863d7ad7939e91e90ffa15ef23b065edf29986
Tx public key: 5b9a0f8023927e82abe1caeb887b89a419e8393dd8d9d9047ba48a8cc550ece9
Timestamp: 1698284587 Timestamp [UCT]: 2023-10-26 01:43:07 Age [y:d:h:m:s]: 01:197:11:56:19
Block: 877742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402164 RingCT/type: yes/0
Extra: 015b9a0f8023927e82abe1caeb887b89a419e8393dd8d9d9047ba48a8cc550ece90211000000034b8f5122000000000000000000

1 output(s) for total of 0.758012560000 dcy

stealth address amount amount idx
00: aa2bd35a912613ba5c645ca919335a35271704a47e836c896d3f8379a4e48fd0 0.758012560000 1333128 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": 877752, "vin": [ { "gen": { "height": 877742 } } ], "vout": [ { "amount": 758012560, "target": { "key": "aa2bd35a912613ba5c645ca919335a35271704a47e836c896d3f8379a4e48fd0" } } ], "extra": [ 1, 91, 154, 15, 128, 35, 146, 126, 130, 171, 225, 202, 235, 136, 123, 137, 164, 25, 232, 57, 61, 216, 217, 217, 4, 123, 164, 138, 140, 197, 80, 236, 233, 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