Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe596ababc6170eb5f26c460486f6b0be8bda5eeb1799669a28fef5df446061

Tx prefix hash: 41efd8f6265956ef898055c335a3cf12e7e0e4ce5263fedf7e85dbab8ab0d9cc
Tx public key: a55d837acb2946c70def197e1e1941d27e67fb3af7e0dd3a73ff4aca70c95dc7
Timestamp: 1676902759 Timestamp [UCT]: 2023-02-20 14:19:19 Age [y:d:h:m:s]: 02:054:06:06:02
Block: 701140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560377 RingCT/type: yes/0
Extra: 01a55d837acb2946c70def197e1e1941d27e67fb3af7e0dd3a73ff4aca70c95dc702110000000374b6d784000000000000000000

1 output(s) for total of 2.916298903000 dcy

stealth address amount amount idx
00: 1b45145564930ad80f8c23db23fe1c8a51d68b4c266846637e531b6a7ca231ac 2.916298903000 1144605 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": 701150, "vin": [ { "gen": { "height": 701140 } } ], "vout": [ { "amount": 2916298903, "target": { "key": "1b45145564930ad80f8c23db23fe1c8a51d68b4c266846637e531b6a7ca231ac" } } ], "extra": [ 1, 165, 93, 131, 122, 203, 41, 70, 199, 13, 239, 25, 126, 30, 25, 65, 210, 126, 103, 251, 58, 247, 224, 221, 58, 115, 255, 74, 202, 112, 201, 93, 199, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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