Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0bc087c5824adc1d953042eca44300168d248f3cc78aa6fde4a871f7b951a0d

Tx prefix hash: d9c26bcea714c5b911b5f004369393fd1e874695755adb2cf32e7281998f39dc
Tx public key: 55974b8f9933bed382f4a86c633b760f0606d6d456a167da74cbb65f22482c0f
Timestamp: 1707964784 Timestamp [UCT]: 2024-02-15 02:39:44 Age [y:d:h:m:s]: 01:049:09:24:20
Block: 957766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296346 RingCT/type: yes/0
Extra: 0155974b8f9933bed382f4a86c633b760f0606d6d456a167da74cbb65f22482c0f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b36afbfcf9ee16aa1059c226444a2ee4c75cbe6db2a939e0dc7eea03f468abfc 0.600000000000 1417115 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": 957776, "vin": [ { "gen": { "height": 957766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b36afbfcf9ee16aa1059c226444a2ee4c75cbe6db2a939e0dc7eea03f468abfc" } } ], "extra": [ 1, 85, 151, 75, 143, 153, 51, 190, 211, 130, 244, 168, 108, 99, 59, 118, 15, 6, 6, 214, 212, 86, 161, 103, 218, 116, 203, 182, 95, 34, 72, 44, 15, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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