Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bab25032ae0f1966ec37552618fa3021ab4965dcab4e7d8a44990cef15b893d2

Tx prefix hash: 77d7ab97fa553ec15ca44378a02c489a1a8ae54433a8a0aa6a1c2175ccaa42bc
Tx public key: e348dbdd865ca6431f6e9ce57ca7e39da765b4dfaa14c1d16e22b9e350df8f4a
Timestamp: 1709393086 Timestamp [UCT]: 2024-03-02 15:24:46 Age [y:d:h:m:s]: 01:038:05:08:39
Block: 969626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288308 RingCT/type: yes/0
Extra: 01e348dbdd865ca6431f6e9ce57ca7e39da765b4dfaa14c1d16e22b9e350df8f4a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2139e086cfde3f8e944b7fc6ad6b0c6987389da45e0673aba3f89e12d4fa0ab5 0.600000000000 1429463 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": 969636, "vin": [ { "gen": { "height": 969626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2139e086cfde3f8e944b7fc6ad6b0c6987389da45e0673aba3f89e12d4fa0ab5" } } ], "extra": [ 1, 227, 72, 219, 221, 134, 92, 166, 67, 31, 110, 156, 229, 124, 167, 227, 157, 167, 101, 180, 223, 170, 20, 193, 209, 110, 34, 185, 227, 80, 223, 143, 74, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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