Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5a12d4ba24dedf308ab4bd49095721bfbdde121e10f76b923d0e14fc37d7a26

Tx prefix hash: a2b30c9d04caf60be30ad9c8a0a2b454c0995e8f579c0b420f72399b980c5d2a
Tx public key: 7cfcddd5e4d096c9441058cf4b1da4346e4fb5a40eebe215913e0e899ab0a3b6
Timestamp: 1696796375 Timestamp [UCT]: 2023-10-08 20:19:35 Age [y:d:h:m:s]: 01:191:22:49:25
Block: 865400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398209 RingCT/type: yes/0
Extra: 017cfcddd5e4d096c9441058cf4b1da4346e4fb5a40eebe215913e0e899ab0a3b602110000000141ee1c9b000000000000000000

1 output(s) for total of 0.832857286000 dcy

stealth address amount amount idx
00: de1f445cc6f522d86c646079cf34eb7ec981da2f11186439cd4cfe74a348f9f1 0.832857286000 1319932 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": 865410, "vin": [ { "gen": { "height": 865400 } } ], "vout": [ { "amount": 832857286, "target": { "key": "de1f445cc6f522d86c646079cf34eb7ec981da2f11186439cd4cfe74a348f9f1" } } ], "extra": [ 1, 124, 252, 221, 213, 228, 208, 150, 201, 68, 16, 88, 207, 75, 29, 164, 52, 110, 79, 181, 164, 14, 235, 226, 21, 145, 62, 14, 137, 154, 176, 163, 182, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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