Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a7a93f4ab308ca7169a198e830990d262d277f04162673e84b3c8c8809f5fc2

Tx prefix hash: baeafca3b8b356b6f73c5cb26678b0ea4dcfc0a1a14ae037fae927019699e3e5
Tx public key: 0fe4c9dbf86a78ff691045fe0e48685f44f120b9d47a426617f5a4c571d4b4eb
Timestamp: 1723151214 Timestamp [UCT]: 2024-08-08 21:06:54 Age [y:d:h:m:s]: 00:301:10:08:29
Block: 1083677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215363 RingCT/type: yes/0
Extra: 010fe4c9dbf86a78ff691045fe0e48685f44f120b9d47a426617f5a4c571d4b4eb021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 955867105a14ad3b3609d4b7a44beae1b78e84777a80473d9cb798c4177ee502 0.600000000000 1557684 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": 1083687, "vin": [ { "gen": { "height": 1083677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "955867105a14ad3b3609d4b7a44beae1b78e84777a80473d9cb798c4177ee502" } } ], "extra": [ 1, 15, 228, 201, 219, 248, 106, 120, 255, 105, 16, 69, 254, 14, 72, 104, 95, 68, 241, 32, 185, 212, 122, 66, 102, 23, 245, 164, 197, 113, 212, 180, 235, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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