Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d30c87f90a4340e02c8c1b88b906c0227ef073b3e4f0d56d2587b9dc7560a56c

Tx prefix hash: 95677892986e3039f5fa341becfc38e559b22ce9e28cda3248e7492be8c71a7e
Tx public key: aa676f4180235525eaaa308df6ac322c435e419d7cf1e9ff4903048fb4918db5
Timestamp: 1706881631 Timestamp [UCT]: 2024-02-02 13:47:11 Age [y:d:h:m:s]: 01:078:13:42:58
Block: 948789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317215 RingCT/type: yes/0
Extra: 01aa676f4180235525eaaa308df6ac322c435e419d7cf1e9ff4903048fb4918db50211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1918302788a5c305d14106dc316c327e53b7cf7b795acf6a924af82b0d65a685 0.600000000000 1407271 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": 948799, "vin": [ { "gen": { "height": 948789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1918302788a5c305d14106dc316c327e53b7cf7b795acf6a924af82b0d65a685" } } ], "extra": [ 1, 170, 103, 111, 65, 128, 35, 85, 37, 234, 170, 48, 141, 246, 172, 50, 44, 67, 94, 65, 157, 124, 241, 233, 255, 73, 3, 4, 143, 180, 145, 141, 181, 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