Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76e8959d5eacc9f67540798e1085979d3cae0040d550473c2fd13b30b67a923e

Tx prefix hash: 6122c077295ebaa088cd8603408fdebe44c2c2d1db92d9d92526262a4f885de4
Tx public key: df7664ebabf62d599e0c85a77011dc6baae25bc230d1d365f3bc1b0ebf81a448
Timestamp: 1702712081 Timestamp [UCT]: 2023-12-16 07:34:41 Age [y:d:h:m:s]: 01:074:15:26:03
Block: 914226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314448 RingCT/type: yes/0
Extra: 01df7664ebabf62d599e0c85a77011dc6baae25bc230d1d365f3bc1b0ebf81a44802110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01a7ae1aaef1ed00693849067ae2ec3f28a48d5eb7865fa074dcd948761a9733 0.600000000000 1371512 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": 914236, "vin": [ { "gen": { "height": 914226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01a7ae1aaef1ed00693849067ae2ec3f28a48d5eb7865fa074dcd948761a9733" } } ], "extra": [ 1, 223, 118, 100, 235, 171, 246, 45, 89, 158, 12, 133, 167, 112, 17, 220, 107, 170, 226, 91, 194, 48, 209, 211, 101, 243, 188, 27, 14, 191, 129, 164, 72, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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