Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c61c41adc3701e20147dca76e8211e930b68469f9ea3fbe3aa135df518e764fe

Tx prefix hash: 6b38e3e5535d5cee496a5acb7be2ab289b2839af24bce41e29361b3495283175
Tx public key: 97a28c6b02a211a99de5410e16a8a1b51ed1f0596368de50f36cd12bc30c8cf6
Timestamp: 1710852304 Timestamp [UCT]: 2024-03-19 12:45:04 Age [y:d:h:m:s]: 01:047:01:39:44
Block: 981728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294630 RingCT/type: yes/0
Extra: 0197a28c6b02a211a99de5410e16a8a1b51ed1f0596368de50f36cd12bc30c8cf602110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69877e5dffbb6eaed2ab8f9adf0f1d26955131488e6feff4e293bec8af8407f2 0.600000000000 1441825 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": 981738, "vin": [ { "gen": { "height": 981728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69877e5dffbb6eaed2ab8f9adf0f1d26955131488e6feff4e293bec8af8407f2" } } ], "extra": [ 1, 151, 162, 140, 107, 2, 162, 17, 169, 157, 229, 65, 14, 22, 168, 161, 181, 30, 209, 240, 89, 99, 104, 222, 80, 243, 108, 209, 43, 195, 12, 140, 246, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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