Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fc6f409d17d02fbfb7f84b0f26ebdabfd5b6fae831ea8f8eb22b750427e4285

Tx prefix hash: 79a7659a03747a0aaa01b67f3bcadf83f4b378df00f04c480fc1d55b2a9c7451
Tx public key: d7d695d0a7fe18732168b41d69337610824426b44ab4c61b36e481fe852f36e2
Timestamp: 1673207479 Timestamp [UCT]: 2023-01-08 19:51:19 Age [y:d:h:m:s]: 02:070:15:48:18
Block: 670478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572198 RingCT/type: yes/0
Extra: 01d7d695d0a7fe18732168b41d69337610824426b44ab4c61b36e481fe852f36e202110000000274b6d784000000000000000000

1 output(s) for total of 3.684919577000 dcy

stealth address amount amount idx
00: faf1ac5d39dd0a7012d0141e5a3952dc00e7653b5043334435c1fe1e6289f13a 3.684919577000 1111885 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": 670488, "vin": [ { "gen": { "height": 670478 } } ], "vout": [ { "amount": 3684919577, "target": { "key": "faf1ac5d39dd0a7012d0141e5a3952dc00e7653b5043334435c1fe1e6289f13a" } } ], "extra": [ 1, 215, 214, 149, 208, 167, 254, 24, 115, 33, 104, 180, 29, 105, 51, 118, 16, 130, 68, 38, 180, 74, 180, 198, 27, 54, 228, 129, 254, 133, 47, 54, 226, 2, 17, 0, 0, 0, 2, 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