Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c6d082215d8cf03eba5f5f1f132d91b90ed87a2d5c83a64766e8ac0429585a

Tx prefix hash: b1969e59c7aeb495c441550c16184b449f47b5d7899c620dace5810237f4d1e7
Tx public key: 3a6097adc206bcb80c04e76ef9595ee3efeb4c1e1ac6a44ace07ca585047cb76
Timestamp: 1720691903 Timestamp [UCT]: 2024-07-11 09:58:23 Age [y:d:h:m:s]: 01:123:03:31:23
Block: 1063304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346522 RingCT/type: yes/0
Extra: 013a6097adc206bcb80c04e76ef9595ee3efeb4c1e1ac6a44ace07ca585047cb76021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78f1bc7f3eab89d31be43e8b9ee1553aa2df67f17b24e06438a3004aa2a9768c 0.600000000000 1533819 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": 1063314, "vin": [ { "gen": { "height": 1063304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78f1bc7f3eab89d31be43e8b9ee1553aa2df67f17b24e06438a3004aa2a9768c" } } ], "extra": [ 1, 58, 96, 151, 173, 194, 6, 188, 184, 12, 4, 231, 110, 249, 89, 94, 227, 239, 235, 76, 30, 26, 198, 164, 74, 206, 7, 202, 88, 80, 71, 203, 118, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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