Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99dd254d7b30713c563f4898b996ddea90c150e393ce3a8e34394dfc8c79ccd9

Tx prefix hash: 22f7492f3e0fefd2d04e0c16fac3ed383c4e0fdb617a205b563c83c71f785d7c
Tx public key: 45edeae94b94366e299e68ef48b9051b26cf8b1e120751d916b9eaf9d02f2d71
Timestamp: 1699472846 Timestamp [UCT]: 2023-11-08 19:47:26 Age [y:d:h:m:s]: 01:149:14:43:14
Block: 887381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368116 RingCT/type: yes/0
Extra: 0145edeae94b94366e299e68ef48b9051b26cf8b1e120751d916b9eaf9d02f2d71021100000002679a8a81000000000000000000

1 output(s) for total of 0.704268687000 dcy

stealth address amount amount idx
00: 790770e3bb268b50919b7d35f876ec211e7c012d95273cfb12cbd73110033e52 0.704268687000 1343258 of 0

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": 887391, "vin": [ { "gen": { "height": 887381 } } ], "vout": [ { "amount": 704268687, "target": { "key": "790770e3bb268b50919b7d35f876ec211e7c012d95273cfb12cbd73110033e52" } } ], "extra": [ 1, 69, 237, 234, 233, 75, 148, 54, 110, 41, 158, 104, 239, 72, 185, 5, 27, 38, 207, 139, 30, 18, 7, 81, 217, 22, 185, 234, 249, 208, 47, 45, 113, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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