Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389780c81f726e10ef30e0903ce6cc6ce660831a71302c73dc841a81dd9983f3

Tx prefix hash: 6f77574a82c6958c94e7ff60c7ab8b47138ec9d91b743e7e57c3dadc4c0f60e0
Tx public key: 7d5069bf0a904fccdd0652c6a8f86cbb645ad47494f8d4ac1667df7aa4f05bc2
Timestamp: 1699130772 Timestamp [UCT]: 2023-11-04 20:46:12 Age [y:d:h:m:s]: 01:086:02:42:49
Block: 884790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322462 RingCT/type: yes/0
Extra: 017d5069bf0a904fccdd0652c6a8f86cbb645ad47494f8d4ac1667df7aa4f05bc2021100000001faf35c9c000000000000000000

1 output(s) for total of 0.718329069000 dcy

stealth address amount amount idx
00: 500b92cb325439c8b0a6ca696276c623466bf007190f836aaf741f0286d5a6dc 0.718329069000 1340537 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": 884800, "vin": [ { "gen": { "height": 884790 } } ], "vout": [ { "amount": 718329069, "target": { "key": "500b92cb325439c8b0a6ca696276c623466bf007190f836aaf741f0286d5a6dc" } } ], "extra": [ 1, 125, 80, 105, 191, 10, 144, 79, 204, 221, 6, 82, 198, 168, 248, 108, 187, 100, 90, 212, 116, 148, 248, 212, 172, 22, 103, 223, 122, 164, 240, 91, 194, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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