Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78b8cd0cdad8e638d80ffcd118856d423f43fb52cdee19c5fe79923aebd21824

Tx prefix hash: 309cd2ae41ad97eb8d9615ebc68c6bed0c08d933e1da0fded504fe51faace526
Tx public key: 3dd183bd7cf300bd9f18bea38fd637d98366d50c3f5e02a10ee5df7f9b690049
Timestamp: 1720858645 Timestamp [UCT]: 2024-07-13 08:17:25 Age [y:d:h:m:s]: 00:304:12:25:02
Block: 1064693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217579 RingCT/type: yes/0
Extra: 013dd183bd7cf300bd9f18bea38fd637d98366d50c3f5e02a10ee5df7f9b69004902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43f87265b000f727ee712950a7670b7bc4bbf37674b676e19c7b1a16a7279974 0.600000000000 1535224 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": 1064703, "vin": [ { "gen": { "height": 1064693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43f87265b000f727ee712950a7670b7bc4bbf37674b676e19c7b1a16a7279974" } } ], "extra": [ 1, 61, 209, 131, 189, 124, 243, 0, 189, 159, 24, 190, 163, 143, 214, 55, 217, 131, 102, 213, 12, 63, 94, 2, 161, 14, 229, 223, 127, 155, 105, 0, 73, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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