Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec106cfe05ae655f728b6ec73062c1a0f775948f140c74b4c1295abfd968326

Tx prefix hash: 2885dbcc9223d19d0eae1fa7f369dfd99738d9bd0001f2e339d397c793985dab
Tx public key: b2b5287625d2b95a382aba081e0d9c14a477937bb1ecdc9f521df6a1e1ba0f51
Timestamp: 1705449229 Timestamp [UCT]: 2024-01-16 23:53:49 Age [y:d:h:m:s]: 01:092:09:32:09
Block: 936895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327156 RingCT/type: yes/0
Extra: 01b2b5287625d2b95a382aba081e0d9c14a477937bb1ecdc9f521df6a1e1ba0f5102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a934613ac34aa4c179e637b19661bacf455f529f3b1c1cd1f6c9b0d2ae25c04b 0.600000000000 1394937 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": 936905, "vin": [ { "gen": { "height": 936895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a934613ac34aa4c179e637b19661bacf455f529f3b1c1cd1f6c9b0d2ae25c04b" } } ], "extra": [ 1, 178, 181, 40, 118, 37, 210, 185, 90, 56, 42, 186, 8, 30, 13, 156, 20, 164, 119, 147, 123, 177, 236, 220, 159, 82, 29, 246, 161, 225, 186, 15, 81, 2, 17, 0, 0, 0, 5, 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